[BUG]: fix binary search impl of LimitOperator#3489
Merged
codetheweb merged 2 commits intomainfrom Jan 15, 2025
Merged
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
979bfd5 to
ca18e20
Compare
Sicheng-Pan
reviewed
Jan 14, 2025
ca18e20 to
69c4d73
Compare
Collaborator
|
Could we hardcode the repro that caused this if it was a prop test? |
Contributor
Author
Added |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes
This has been materializing as a flaky test, but is an actual correctness bug. Reproduced in a Python test and tracked down to this operator.
Test plan
How are these changes tested?
pytestfor python,yarn testfor js,cargo testfor rustAdded test was previously failing.
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?
n/a